Skip to content

packaging: one package for full and pruned storage - #113

Merged
EnzinoBB merged 1 commit into
masterfrom
packaging/single-package
Oct 26, 2026
Merged

EnzinoBB merged 1 commit into
masterfrom
packaging/single-package

Conversation

@EnzinoBB

Copy link
Copy Markdown
Collaborator

The full and pruned packages differed only in config.ini, and each carried the ~200 MB JDK. Now each build (linux-x64, linux-x64-glibc2.31) has one package: config.ini runs a full node (as the official release), config.pruned.ini a pruned one on LMDB (./node --config-file config.pruned.ini). About 475 MB less per release.

  • make-package.sh without the variant argument; README-COMMUNITY.txt explains both files.
  • release.yml: two packages instead of four; the Docker image from the new package (its entrypoint writes [storage] itself).
  • snapshot.yml, known-hosts.yml, run-weekly.sh, docker.yml, db-compare.yml: download the new name or the old one (community.13 and earlier), and copy config.pruned.ini over config.ini where they run a pruned node.
  • Docs: differences.md, storage.md, README, CHANGES.

🤖 Generated with Claude Code

The packages differed only in config.ini: one package per build now holds
config.ini (full, as the official release) and config.pruned.ini (pruned on
LMDB), half the release size. The workflows that take the latest release's
package accept the old and the new layout, and copy config.pruned.ini over
config.ini where they run a pruned node.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@EnzinoBB
EnzinoBB merged commit 075f72a into master Oct 26, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant